If route.fetch() succeeds but subsequent processing (like resp.json() or mask()) throws an exception, calling route.continue_() will fail because Playwright does not allow continuing a route after it has already been fetched. This will raise another exception and leave the request hung indefinitely. Fulfill the route with the original response instead if route.fetch() succeeded.

def make_route_handler(mock_all=False):
    def handle(route):
        url = route.request.url
        if 'stream' in url:
            return route.continue_()
        if mock_all:
            data = build_mock(url, route.request.method)
            if data is not None:
                try:
                    return route.fulfill(status=200, content_type='application/json',
                                         body=json.dumps(data, ensure_ascii=False))
                except Exception:
                    pass
        resp = None
        try:
            resp = route.fetch()
            ct = (resp.headers or {}).get('content-type', '')
            if 'application/json' not in ct:
                return route.fulfill(response=resp)
            body = json.dumps(mask(resp.json()), ensure_ascii=False)
            return route.fulfill(response=resp, body=body, content_type='application/json')
        except Exception:
            if resp is not None:
                try:
                    return route.fulfill(response=resp)
                except Exception:
                    return
            else:
                try:
                    return route.continue_()
                except Exception:
                    return
    return handle

The current regular expression only matches single-quoted values (e.g., title='...'). If the API response or configuration uses double quotes, the metadata masking will be bypassed. Update the regex to support both single and double quotes to ensure robust masking.

If the login fails (e.g., due to incorrect credentials), the script will continue capturing other pages, which will all redirect to the login page or show unauthorized errors. This results in broken screenshots. Add a check to verify that the login was successful and raise an error early if it failed.

GitHub's heading-anchor algorithm (github-slugger) collapses consecutive spaces/hyphens into a single hyphen and strips leading/trailing hyphens. The current implementation only replaces spaces with hyphens, which can lead to false positives (e.g., reporting broken links) for headings with multiple spaces or consecutive punctuation. Update slugify to match GitHub's behavior more accurately.